<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
	<TITLE></TITLE>
	<META NAME="GENERATOR" CONTENT="OpenOffice.org 2.3  (Win32)">
	<META NAME="AUTHOR" CONTENT="*">
	<META NAME="CREATED" CONTENT="20080304;14300000">
	<META NAME="CHANGEDBY" CONTENT="Sean Fabri">
	<META NAME="CHANGED" CONTENT="20080310;14465961">
	<STYLE TYPE="text/css">
	<!--
		@page { size: 21cm 29.7cm; margin: 2.54cm }
		P { margin-bottom: 0.21cm; direction: ltr; color: #000000; line-height: 115%; widows: 2; orphans: 2 }
		P.western { font-family: "Calibri", sans-serif; font-size: 11pt; so-language: en-GB }
		P.cjk { font-family: "Calibri", sans-serif; font-size: 11pt }
		P.ctl { font-family: "Calibri", sans-serif; font-size: 11pt; so-language: ar-SA }
	-->
	</STYLE>
</HEAD>
<BODY LANG="en-GB" TEXT="#000000" DIR="LTR">
<P CLASS="western" ALIGN=CENTER STYLE="margin-bottom: 0.35cm; line-height: 100%">
<FONT SIZE=5><U>Software Engineering</U></FONT></P>
<P CLASS="western" ALIGN=CENTER STYLE="margin-bottom: 0.35cm; line-height: 100%">
<FONT SIZE=5><U>House 6</U></FONT></P>
<P CLASS="western" STYLE="margin-bottom: 0.35cm; line-height: 100%"><FONT SIZE=4 STYLE="font-size: 16pt"><B>Document
Title: </B></FONT>Requirements_Specification.html</P>
<P CLASS="western" STYLE="margin-bottom: 0.35cm; line-height: 100%"><FONT SIZE=4 STYLE="font-size: 16pt"><SPAN LANG="fr-FR"><B>Document
Version: </B></SPAN></FONT><FONT SIZE=2 STYLE="font-size: 11pt"><SPAN LANG="fr-FR"><SPAN STYLE="font-weight: medium">1.0</SPAN></SPAN></FONT><SPAN LANG="fr-FR">
(03.03.08)</SPAN></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><FONT SIZE=4 STYLE="font-size: 16pt"><SPAN LANG="fr-FR"><B>Document
Author: </B></SPAN></FONT><SPAN LANG="fr-FR">Jean-Marc Jones,
</SPAN>Vassilis Iliopoulos, Design Team</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P CLASS="western" STYLE="margin-bottom: 0.35cm; line-height: 100%"><FONT SIZE=4 STYLE="font-size: 16pt"><B>Audited
By: </B></FONT>Ben Jones</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><FONT SIZE=4 STYLE="font-size: 16pt"><B>Introduction</B></FONT></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">We have been asked
to implement a simple <B>HTML renderer</B> for a meat packing
company, to be used by farmers.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>i.e. a program
which reads a document written in HTML, and formats it for a display
or printer. HTML renderers are included in web browsers like
Netscape, Internet Explorer, Mozilla Firefox etc.</I></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">What we need for
this project is a Java program to render an HTML document in a Java
window that is reading and displaying a document written in HTML,
including some extensions.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">Since the software
won&rsquo;t be used by computer literate staff the main features of
it should be as trivial as possible: user friendly and simple
Graphical User Interface, no confusing error messages, readable text
in times roman, etc.  
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">From the customer
meeting a few weeks ago there were a few extensions our team was
committed to, for example underlining text, the ability to change
font size and colour in the GUI, one level of nested tables, string
searching and error logging.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">There are also other
optional extensions that may be incorporated into the software, such
as image rendering, further levels of nested tables, error diagnosis
and outputting to a PDF file.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">This requirements
specification includes the following diagrams:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<UL>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">Use case
	diagram</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">Basic class
	diagram</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">
	Activity(Swimlane) diagram</P>
</UL>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">The following
diagrams were excluded:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<UL>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">Sequence
	diagram</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">State diagram</P>
</UL>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">CRC cards have also
been developed and will be used by the design and programming teams
as the basis for their implementation of the software.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><FONT SIZE=4 STYLE="font-size: 16pt"><B>Analysis
Model</B></FONT></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><FONT SIZE=3><U>Use
Case Text</U></FONT></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><B>Scenarios</B></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>View File
Scenario:</I></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">The farmer has a
file he wishes to view; he selects the file he wants to open on the
screen and the file is then converted into readable text. Once the
file is ready it will be displayed for the farmer on the screen. 
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>File Printing
Scenario:</I></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">There is a page the
customer wants to print on screen; the farmer selects the print
option and the displayed text is sent to a file, which is capable of
displaying the text without having to use the system.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Edit Display Text
Scenario:</I></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">The farmer decides
that he wants to change the appearance of the current font on the
system; the change font option is selected and a new window is
displayed on the screen. In this window the famer has the option to
change the font size, type and colour. Once the farmer is satisfied
with the alterations he has made and selects the save changes option,
he is returned to the start screen.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Search file
scenario:</I></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">The farmer has a
file open and there is specific text that he wants to search for; he
will select the search option, input the text that he wants to find,
and once the search is run any matches with the entered text will be
displayed on the screen.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Admin Views Error
Report Scenario:</I></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">The admin has been
called to fix an error. To find out the nature of the error, he will
select the view error log option and a file with the error that has
been detected is displayed with information about each specific error
logged.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><FONT SIZE=3><U>Use
Case Content</U></FONT></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><B>View File</B></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Primary Scenario</I>:</P>
<OL>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">System displays
	the start window on the screen when the farmer double-clicks on the
	program&rsquo;s icon.</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">Farmer selects
	a file he wants to view.</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">Farmer chooses
	the open file option.</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">System converts
	the file into readable text.</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">System displays
	the file on to the screen.</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">Farmer selects
	to return to the start window.</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">System displays
	the start window.</P>
</OL>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Secondary
Scenario</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">1-a:  Admin wants to
view the error log.</P>
<OL TYPE=i>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">Admin selects
	the view error log option.</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">System displays
	a file with all the errors that have been thrown.</P>
</OL>
<P STYLE="margin-bottom: 0cm; line-height: 100%">5-a:  Farmer wants
to print an opened file.</P>
<OL TYPE=i>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">Farmer selects
	the print option.</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">System puts the
	displayed text into a file that can be saved in the current format.</P>
</OL>
<P STYLE="margin-bottom: 0cm; line-height: 100%">5-b:  Farmer wants
to change font style. 
</P>
<OL TYPE=i>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">Farmer selects
	his desired changes to font size, type and colour.</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">System changes
	the font style to the selected settings.</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">System displays
	the opened file in new font settings.</P>
</OL>
<P STYLE="margin-bottom: 0cm; line-height: 100%">5-c: Farmer wants to
search opened file.</P>
<OL TYPE=i>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">Farmer enters
	the text he wants to search for.</P>
	<LI><P STYLE="margin-bottom: 0cm; line-height: 100%">System displays
	the search matches.</P>
</OL>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><FONT SIZE=3><U>Use
Case Diagrams</U></FONT></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Description</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">A use case diagram
is a type of scenario based UML notation diagram. Use cases will show
how a system works from the standpoint of an external observer. The
use case is a versatile way of viewing a system in terms of its
actors and their goals. These diagrams present this information in a
graphical view of the systems functionality. 
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Reason of use</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">Use case diagram
prove extremely useful in OOA (Object Orientated Analysis) as they
allow you to discover new requirements as you create them. This is
due to further analysis of your system, showing you new areas that
need improving. Use cases can also prove useful for communication
with your client or for test cases.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P LANG="" CLASS="western" STYLE="margin-bottom: 0.35cm"><IMG SRC="Requirements_Specification_html_m39abc677.png" NAME="Picture 1" ALIGN=BOTTOM WIDTH=601 HEIGHT=393 BORDER=0></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Explanation</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">This use case has
two actors; the farmer (user) and an admin. The user can perform a
number of tasks including some which will display an output into the
GUI for the Renderer, or write a string to a PDF file. The admin can
view an error report displaying the line numbers in the code where
the error has occurred, there is also a possibility that contained
within the report will be a suggestion specifying what the problem in
the code might be.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><FONT SIZE=3><U>CRC
Cards</U></FONT></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P CLASS="western" STYLE="margin-bottom: 0cm; line-height: 100%">These
are the final CRC cards, representing the responsibilities and
collaborators of each class. 
</P>
<P CLASS="western" STYLE="margin-bottom: 0cm; line-height: 100%">It
contains all the methods of the classes converted into text, as well
as the collaborating classes which they extend or depend upon.</P>
<P CLASS="western" STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">They are based on
the class diagram of the analysis team, and have been passed on to
the design team to take it further.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><IMG SRC="Requirements_Specification_html_5bf8978f.png" NAME="graphics1" ALIGN=BOTTOM WIDTH=578 HEIGHT=930 BORDER=0></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><FONT SIZE=3><U>Basic
Class Diagrams</U></FONT></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Description</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">The class diagram is
used in UML to define the different classes and objects that will be
in a computer system. The class diagram will also show different
types of relationships between these classes. In some class diagrams
the method and attributes of the classes will be shown, however for
the basic class diagrams we will just be showing the bare minimum.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Reason of use</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">Class diagrams like
this can be useful as they just show the most basic structure of the
program, allowing the design team to develop on this by inserting
more specific relationships, variables and methods into the diagram.
Once completed, this can then be used by the programming team as the
basis for their coding. This class diagram has been based on the
visitor design pattern with a few layout ideas from the GML Renderer.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P LANG="" STYLE="margin-bottom: 0cm; line-height: 100%"><IMG SRC="Requirements_Specification_html_m27b1139.png" NAME="Picture 3" ALIGN=BOTTOM WIDTH=441 HEIGHT=521 BORDER=0></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Explanation</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">Above we can see the
basic layout of the classes and their base relationships. At the top
of the diagram we have the ErrorCatcher, Parser, Renderer and
RendererGUI. The user will select a file to be rendered from the GUI
and this will tell the parser to create the tree from the
RendererNode super class structure. Once this has been done the
render can use the tree to convert from the HTML file to a text file
that can be displayed in the GUI. If an error occurs the ErrorCatcher
will send the information back to the GUI to be displayed. 
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><FONT SIZE=3><U>Activity
(Swimlane) Diagrams:</U></FONT></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Description</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">Activity diagrams
are considered as flow process diagrams that represent the actors
working on a particular activity or process. When these swim lanes
are observed, it becomes clear how each actor&rsquo;s action affects
the rest of the program and thus the overall layout of each process.
They use dots to declare starting/ending points, with arrows that
connect each process phase. Each action is also placed in the swim
lane of the actor&rsquo;s responsible for it, which is described by
an activity rectangle.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Reason of use</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">It allows the
modeller to represent the flow of activities described by the
use-case.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">This method of
diagramming allows us to quickly and easily plot and trace processes
and, in particular, the interconnections between processes, and the
actors involved.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P LANG="" STYLE="margin-bottom: 0cm; line-height: 100%"><IMG SRC="Requirements_Specification_html_m62158689.png" NAME="Picture 4" ALIGN=BOTTOM WIDTH=432 HEIGHT=929 BORDER=0></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Explanation</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">This particular
diagram consists of four actors: Parser, Renderer, RenderGUI and
User.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">It follows the use
case specification step by step, providing an overall view of how the
renderer is supposed to work after its completion. 
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><FONT SIZE=3><U>Sequence
Diagrams</U></FONT></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Description</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">A sequence diagram
is a type of interaction diagram; these are used in UML to describe
the behaviour of groups of objects.  A sequence diagram is
predominately used to view the behaviour of a single scenario. This
produces the specification of simple runtime in a simple graphical
view.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Reason of
exclusion</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">In our phase plan we
decided that the analysis team would be creating the sequence
diagrams, however as we progressed with the project and collaborated
with the design team we decided that it would be better to have them
implement the sequence diagrams in their high-level design. The
reason for this was that these diagrams fit better into the
architectural design, rather than into the requirements of the system
which focuses on what the system is doing rather than on how it does
it.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><FONT SIZE=3><U>State
Diagrams</U></FONT></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Description</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">A state diagram is
used to show how the transitions can cause an object to change state
and the available states of that object. 
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><I>Reason of
exclusion</I>:</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">As a state diagram
is primarily used for describing the object behaviour in several use
cases it would not be appropriate for us to use them considering we
only have one consolidated use case diagram. Instead we have opted to
use a modified activity diagram called a Swimlane, as they are a
better fit with the system we are building. The reason for this is
that they show a sequence of activities for some use cases and
objects.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><FONT SIZE=4 STYLE="font-size: 16pt"><B>Bibliography</B></FONT></P>
<P STYLE="margin-bottom: 0cm; line-height: 100%"><BR>
</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">1.</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">Martin Fowler</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">UML Distilled: A
brief Guide to The Standard Object Modelling Language</P>
<P STYLE="margin-bottom: 0cm; line-height: 100%">Third Edition (2004)</P>
<P CLASS="western" STYLE="margin-bottom: 0.35cm"><BR><BR>
</P>
<P CLASS="western" STYLE="margin-bottom: 0.35cm"><BR><BR>
</P>
</BODY>
</HTML>